Methods for location of persons with electronic wearables

ABSTRACT

Methods, computer readable storage medium, and systems for mobile devices to locate persons or places are described. In a feature, the invention is a method implemented in a server for providing beaconing sequences to the mobile devices for location sharing. In a feature, the invention is a server executing a method of locating a user using a beaconing mobile device. In a feature, the invention is a non-transitory computer readable medium on a server that encodes a program to execute a method on a first mobile device that determine directions and/or distance between the first mobile device and a second mobile device. In a feature, the invention is a server executing a method to remember a place on a mobile device.

This application is a continuation of U.S. application Ser. No.15/096,258, which was filed on Apr. 11, 2016, which is a continuation ofU.S. application Ser. No. 14/092,846, which was filed on Nov. 27, 2013,which are both incorporated by reference herein.

BACKGROUND

This invention relates to methods and systems for locating persons andplaces using mobile devices.

People attend events where they want to meet up with friends andacquaintances. If there is a large crowd at the event, it can bedifficult for people to locate each other. Sometimes last minute changesin plans also prevent meeting up. Other times the problem is findingexactly where one parked the car after the event. Because many peoplecarry mobile devices (e.g., cellphones), it would be useful to providemethods and systems for locating persons and places that could beimplemented with mobile devices in these and other circumstances.

SUMMARY OF THE INVENTION

This invention relates to systems and methods for locating persons andplace with mobile devices. In a feature, the invention is a methodimplemented in a server for providing beaconing sequences for locationsharing to mobile devices. In a feature, the invention is a serverexecuting a method of locating a user using a beaconing mobile device.In another feature, the invention is a non-transitory computer readablemedium on a server that encodes a program to execute a method on a firstmobile device that determine directions and/or distance between thefirst mobile device and a second mobile device. In a feature, theinvention is a server executing a method to remember a place on a mobiledevice. In still another feature, the invention is a system forproviding beaconing sequences for location sharing to mobile devices.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a network diagram that illustrates N mobile devicescommunicating with N servers.

FIGS. 2A-2F illustrate the user interfaces of a mobile device.

FIG. 3 illustrates user interactions and communications among the mobiledevices and the servers.

FIG. 4 illustrates a second mobile device user locating a first mobiledevice user in a crowd using the compass feature.

FIG. 5 is a perspective view of a second mobile device user locating afirst mobile device user in a crowd using a compass.

FIG. 6 is a perspective view of a second mobile device user locating afirst mobile device user in a crowd using the compass on a smart watchor an electronic wearable.

FIG. 7 illustrates a second mobile device user locating a first mobiledevice user by using a beaconing mobile device in a crowd with otherusers.

FIG. 8 is a perspective view of a second mobile device user locating afirst mobile device user in a crowd by using the beaconing mobiledevice.

FIG. 9 illustrates beaconing sequences used in FIGS. 7-8.

FIG. 10 illustrates a variety of beaconing sequences.

FIG. 11 illustrates assigning beaconing sequences by location cells.

FIG. 12 illustrates some beaconing sequences that could be used inlocation cells.

FIG. 13 illustrates assigning beaconing sequences by venue.

FIG. 14 illustrates examples of beaconing sequences that could be usedin FIG. 13.

FIG. 15 illustrates a flow diagram for the beaconing logic that runs onthe server of FIGS. 1 and 3.

FIG. 16 illustrates a flow diagram for the message logic that runs onthe server of FIGS. 1 and 3.

FIG. 17 illustrates a flow diagram for the event logic that runs on theserver of FIGS. 1 and 3.

FIG. 18A-18F is a set of flow diagrams that illustrate the applicationlogic that runs on the mobile device and interacts with the server.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following description includes the best mode of carrying out theinvention. The detailed description illustrates the principles of theinvention and should not be taken in a limiting sense. The scope of theinvention is determined by reference to the claims. Each part (or step)is assigned its own part (or step) number throughout the specificationand drawings. Because some flow diagrams don't fit on a single drawingsheet, we use capital letters (e.g., “A”) to show how the flow diagramsconnect (e.g., “A” connects the flowcharts of FIGS. 18A-18D).

FIG. 1 is a network diagram that illustrates N mobile devicescommunicating with N servers. The network diagram illustrates a systemthat includes the first mobile device 74, the second mobile 76, thethird mobile device 80 up to the Nth mobile device 84. The communicationlinks 72, 78, 82, and 86 connect the first mobile device 74 through Nthmobile device 84 to the computer network 40 that connects to a firstserver 10 through a communication link 36, a second server 26 through acommunication link 22, and a Nth server 38 through a communication link39.

We now discuss the first server 10 and the second server 26 toillustrate the software and hardware components that can be used toimplement the invention.

The first server 10 illustrates the software components. The firstserver 10 includes a web server 34 that will listen for requests andpass them along to an email server 35, beacon logic 32 (FIG. 15),message logic 28 (FIG. 16), event logic 30 (FIG. 17) that the firstserver 10 executes during operation of the system. A backplane 20 linksthe first server 10, a database and storage 24, the second server 26,and the Nth server 38.

The second server 26 has the same software components (not shown) andillustrates hardware for the first server 10 through Nth server 38. Itincludes a CPU-memory bus 14 that communicates with a processor 12. Thesecond server 26 includes memory 16 coupled to the processor 12 andinterfaces 18 that connect through a communication link 22 to thenetwork 40.

Data is defined as including user data, instructions, and metadata.Inputting data is defined as the input of parameters and data from userinput, computer memory, and/or storage device(s).

A processor could be any suitable general purpose processor runningsoftware. For example, the processor could be one or more multicoreprocessors made by Intel or licensed by ARM, and AMD. In anotherexample, we could use a low cost single board computer processor such asRaspberry Pi. The arrangement and type of the processors is notessential to the invention.

Hennessy and Patterson, Computer Architecture: A Quantitative Approach(2006), and Patterson and Hennessy, Computer organization and Design:The Hardware/Software Interface (2007) describe computer hardware andsoftware, storage systems, and networks and are incorporated byreference.

Each server may run an operating system such as Linux, UNIX, a WindowsOS, or another suitable operating system. Tanenbaum, Modern OperatingSystems (2008) describes operating systems in detail and is herebyincorporated by reference. Bovet and Cesati, Understanding the LinuxKernel (2005), and Bach, Design of the Unix Operating System (1986)describe operating systems in detail and are incorporated by referenceherein.

In an embodiment, each server could be implemented on a virtual machinehosted by VMware, Hyper V, or open source software Xen. Lowe et al.Mastering VMware vSphere 5.5 (2013) describes the VMware virtualizationsoftware in detail and is incorporated by reference herein. Matthews etal., Running Xen: A Hands-On Guide to the Art of Virtualization (2008)describes the free open source Xen virtualization software in detail andis incorporated by reference herein.

In a typical environment, the server will be implemented by hundredseven thousands of computers in a data center such as Amazon WebServices, Google Compute Engine, Microsoft Azure, or Rackspace. It isnot essential to the invention that a particular data center be used.Murty, Programming Amazon Web Services: S3, EC2, SQS, FPS, and SimpleDB(2008) describes the Amazon Web Services in detail and is incorporatedby reference herein. Sanderson, Programming Google App Engine (2012)describes the Google App Engine in detail and is incorporated byreference herein.

In an alternative embodiment, the server will be implemented using lowcost single board computers such as Raspberry Pi that runs locally inthe geographic area and/or near the mobile devices and communicates withthe mobile devices using, for example, network protocols such asBluetooth (e.g., low energy Bluetooth), Wi-Fi, or TCP/IP. Halfacree,Raspberry Pi User Guide (2012) describes this single board computer indetail and is incorporated by reference herein.

The database and storage 24 stores the user and event information andcommunicates with the first server 10, the second server 26, and the Nthserver 38. A non-transitory computer-readable medium (e.g., storagedevice, DVD, USB storage device) can be used to encode the softwareprogram instructions described in the methods below. Rockoff, TheLanguage of SQL: How to Access Data in Relational Databases (2010)describe SQL databases in detail and is incorporated by referenceherein. Redmond et al., Seven Databases in Seven Weeks (2012) describenon-SQL databases in detail and is incorporated by reference herein.

A first mobile device 74 (e.g., a cell phone, a tablet, a smart watch,electronic wearable clothing, or glasses) includes an application 64,including a communication interface 66, application logic 68, and a userinterface 70.

The communication interface 66 includes a conventional network interfacethat enables the first mobile device 74 to communicate through a link 72to a computer network 40, which includes the cellular phone network(e.g. AT&T, Verizon, Sprint, NTT DoCoMo, Orange, and China Mobile)and/or the Internet. Tanenbaum, Computer Networks (2010) describescomputer networks in detail and is incorporated by reference herein.

The user interface 70 defines a set of graphical user interfaces thatwill be displayed on the screen of the mobile device 74 as shown inFIGS. 2A-2F.

The application logic 68 defines the state of the application (e.g.,what screen is being displayed and the mobile device beacon state),stores inputs such as locations of mobile devices obtained from theservers of the computer network 40, and calculates the relativedistances and directions of the mobile devices.

The application logic 68 can be written in a variety of languages. Forexample, if the mobile device is an Apple device the language would beObjective-C. Kochan, Programming in Objective-C (5thEdition)(Developer's Library)(2012) describes Objective-C in detail andis incorporated by reference herein. For example, if the mobile deviceis Android device the language could be Java. Medinieks, ProgrammingAndroid: Java Programming for the New Generation of Mobile Devices(2012) describes Android programming in detail and is incorporated byreference herein.

The first mobile device 74 has a location determination component 52that determines the location of the first mobile device 74 by using avariety of sources. For example, a global positioning system (GPS) 42and cell tower 44 are suitable as long range sources. For shorter rangelocation determination, Wi-Fi 46, Bluetooth 48, including Bluetooth lowenergy (LE), and a RFID protocol such as near field communication (NFC)50 are suitable. Tanenbaum, Computer Networks (2010) describes theseprotocols in detail and is incorporated by reference herein.

The first mobile device 74 has an orientation determination component 58that determines the orientation of the first mobile device 74 withrespect to magnetic north and with respect to the earth's surface byusing a variety of sources. For example, many mobile devices contain anaccelerometer 54 and a compass 56 and gyroscopes (not shown) whichfunction as suitable sources of orientation.

The first mobile device 74 optionally has a map component 62 thatenables the first mobile device 74 to communicate over the Internet witha map provider such as Google maps, Apple maps, Nokia's HERE maps, andOpenStreetMap. It is not essential to the invention which map provideris used.

FIGS. 2A-2F illustrate the details of the user interfaces of a mobiledevice.

FIG. 2A illustrates the first mobile device 74 includes a home screen 88that displays a set of user selectable buttons: a remember place button89, a share location button 90, and a find things button 92.

To illustrate the remember place feature, assume a first user named Alanis using the first mobile device 74 to find his car in a parking lot. IfAlan selects the remember place button 89, the application logic 68 usesthe user interface 70 of the first mobile device 74 to display aremember place screen 94 shown in FIG. 2B.

As shown in FIG. 2B, the screen 94 displays a field 96 that contains thename of the item whose location a user wants to remember. For example,the field 96 is a drop down menu that holds a value for Alan's car: “MyCar” that is associated with location information in the parking lot.

To increase the types of items that can be identified, the field 96 canbe an input field for names entered by the user. After entering thevalue either by menu or text field, the user can save that value byclicking on a save place button 98. The user can tag the item with otherinformation beside or in lieu of the location information by selectingthe “add picture” button 95, the “add voice memo” button 97, and/or the“add text note” button 99, which will call up respectively, the camera,voice memo, and/or text feature of the first mobile device 74. Thus, forAlan to find the place of an item (e.g., where he parked his car orbike, where he left a package, or his favorite store or restaurant) hecan use the remember place feature to store coordinates and/or otherlocation related information.

Referring to FIG. 2A, if Alan wants to share his location with others atan event such as a concert, he will select the share location button 90of the home screen. Now the application logic 68 of the first mobiledevice 74 will display the share location screen 102 on the first mobiledevice 74 as shown in FIG. 2C.

As shown in FIG. 2C, Alan wants to share his location from 6-11 PM withBob, Sarah, and Andrew at an event such as a concert. Alan adds valuesin the input fields such as “Concert” in the event field 101, “6 PM” inthe start time field 103, “11 PM” in the end time field 105, and theemail addresses of Bob, Sarah, and Andrew in a guest field 104. Alanwill then press the send button 106. The email addresses can beretrieved from the contact list of the first mobile device 74 or fromInternet contact lists, e.g., LinkedIn, Facebook, and Yahoo contacts. Onpressing the send button 106, the application logic 68 will use thecommunication interface 66 to send a message to the first server 10(FIG. 1) that will in turn send a message to a second mobile device 76.

Let's now assume a second user “Bob” uses the second mobile device 76that receives the message. Bob will see a new entry “Alan @ Concert” onthe list of the find things screen 108 as shown in FIG. 2D. Before 6 PM,the entry appears, but no distance will be indicated, because the timefor location sharing has not begun. However, at 6 PM, the find thingsscreen 108 will add Alan's current distance and direction from Bob,e.g., Alan is 200 feet NW of Bob. The distance and direction updatesperiodically to track the locations of the first and second mobiledevices 74, 76. At 11 PM, the Alan @ Concert entry 107 may be deletedfrom second mobile device 76 since the time of location sharing is over.

The find things screen 108 optionally includes an on-off slider 111 tomake the second mobile device 76 visible to the first mobile device 74,or make it visible to other mobile devices on the guest list, orinvisible to everybody.

FIG. 2E illustrates the display screen 114 of the second mobile device76 includes a compass 116, a user selectable request to wave button 118,and a beacon indicator 120. As shown, the compass 116 displays that thefirst user Alan is at an event Concert, 200 feet away in the directionof the compass arrow. Optionally, the compass 116 may indicate north ofNWSE directions.

FIG. 2F illustrates the display screen 122 of the first mobile device 74includes a beaconing display 124 that will be used to find the firstuser, Alan as will be described in detail in FIGS. 3-8.

FIG. 3 illustrates interactions and communications among the mobiledevices and a server. Initially, the first user 126 (e.g., Alan) of thefirst mobile device 74 will press a button Start App 125 that will senda HTTP request to compare the clock of the first mobile device 74 withthe clock of the first server 10. That time difference will be stored inthe memory of the first server 10, which will be used by the applicationlater. The first mobile device 74 will display the home screen 88 asshown in FIG. 2A. The first user 126 will press the share locationbutton 90. The first mobile device 74 will display the screen 102 asshown in FIG. 2C. The first user 126 will complete the fields 101, 103,104, and 105 and press the send button 106 as illustrated in FIG. 2C.The first mobile device 74 sends a message 300 to the message logic 28(FIGS. 1 and 16) of the first server 10, which will send a notificationmessage 302 to the second mobile device 76 to notify the second user 128(e.g., Bob) that a new item 107 (e.g., Alan @ Concert) was added to thefind things screen 108 of the second mobile device 76. The first server10 also sends a response 304 to the request 300 to confirm thenotification 127 (e.g., email, text, or push notification) regarding theevent (e.g., Concert) was sent to each guest on the guests list 104.

Next, the second user 128 (e.g., Bob) of the second mobile device 76will start the app 129 that will send a HTTP request to compare theclock of the second mobile device 76 with the clock of the first server10. That time difference will be stored in the memory of the firstserver 10, which will be used by the application later. The secondmobile device 76 will display the home screen 88 as shown in FIG. 2A.The second user 128 will press the find things button 92. The secondmobile device 76 will send a request 306 to the event logic 30 (FIGS. 1and 17) of the first server 10. The first server 10 reads the entries107, 109, and 115 of the find things list in the database 24 (FIG. 1)and sends a response 308 to the second mobile device 76. The response308 includes a list of the entries as illustrated in the find thingsscreen 108 of the second mobile device 76 as shown in FIG. 2D.

The first and second mobile devices 74, 76, as well as the other mobiledevices, periodically update their coordinates to the first server 10that keeps track of their respective locations.

The second user 128 of the second mobile device 76 will press the findbutton 110. The second mobile device 76 will display the compass screen114 as shown in FIG. 2E. The second user 128 of the second mobile device76 will then press the request wave button 118. The second mobile device76 will send a request 310 to the beacon logic 32 (FIGS. 1 and 15) ofthe first server 10. The first server 10 will read a list of users inthe geographic area of interest and each of their beaconing sequences toidentify what beaconing sequence is available for assignment asillustrated in FIG. 15. The first server 10 sends a message 312 with theassigned beaconing sequence 142 (FIG. 9) to the wave screen 122 of thefirst mobile device 74 as illustrated in FIG. 2F. Referring to FIG. 3,the first server 10 sends a response 314 with the assigned beaconingsequence 144 (FIG. 9) to the second mobile device 76. A request to wavewill trigger a beacon sequence on another mobile device so it isconspicuous and can be seen.

The second user 128 (e.g., Bob) now uses the compass 116 to get thedistance (e.g., 200 feet) and direction of the first user 126 (e.g.,Alan). In addition, the second user 128 can use the beaconing sequence144 on the beaconing indicator 120 of his second mobile device 76 toindicate the beaconing sequence 142 being displayed on the first mobiledevice 74. Now the second user 128 will be able to spot the first user126 as long as the first mobile device 74 is visible to the second user128.

FIG. 4 illustrates a crowd gathered at an event such as concert with astage 132. Let's assume the crowd 130 prevents or makes it difficult fora first user 126 (e.g., Alan) and the second user 128 (e.g., Bob) tolocate each other. The first mobile device 74 held by the first user 126beacons which is seen by the second user 128 holding the second mobiledevice 76.

FIG. 5 is a perspective view of FIG. 4 that illustrates how the firstuser is found by the second user. The first user 126 holds the beaconingfirst mobile device 74 (e.g., cell phone) apart from the crowd. Thesecond user 128 holds a second mobile device 76 (e.g., cell phone)displaying a compass 116 that points to the first user 126 and includesa request to wave button 118 that was pressed to trigger beaconing onthe first mobile device 74 and a beacon indicator 120.

FIG. 6 is a perspective view of FIG. 4 that illustrates another contextwhere a first user is found by a second user. The first user 126 holdsthe beaconing first mobile device 74 (e.g., a cell phone or tablet)apart from the crowd. The second user 128 holds or wears a second mobiledevice 77 (e.g., smart watch/electronic wearable) displaying a compass116 that points to the first user 126 and includes a request to wavebutton 118 that was pressed to trigger beaconing on the first mobiledevice 74 and a beacon indicator 120.

FIG. 7 illustrates a crowd gathered at an event such as concert with astage 132. Let's assume the crowd 130 prevents or makes it difficult fora first user 126 (e.g., Alan) and the second user 128 (e.g., Bob) tolocate each other. In addition, unrelated persons at the event are usingour method of location. Thus, the first user 126 is holding a firstmobile device 74, a third user 134 is holding a third mobile device 136,and a fourth user 138 is holding a fourth mobile device 140, which areall beaconing.

FIG. 8 is a perspective view of FIG. 7 that illustrates how our methodwould enable the second user to find the first user despite the presenceof other beaconing mobile devices. The first user 126 holds thebeaconing first mobile device 74 (e.g., cell phone) apart from the crowd130. The second user 128 holds a second mobile device 76 (e.g., cellphone) displaying a compass 116 that points to the first user 126 andincludes a request to wave button 118 that was pressed to triggerbeaconing on the first mobile device 74 and a beacon indicator 120. Thistime, however, the third user 134 is near the first user 126. Thecompass 116 is no longer sufficient to locate the first user 126,because it points generally toward the first user 126 and the third user134. This is one situation where assigning a unique beaconing sequencecan help locate the first user 126.

FIG. 9 illustrates a beaconing sequence that can be flashed to locate aperson in the crowd as shown in FIGS. 7-8. The first mobile device 74includes a screen 124 that flashes a yellow green beaconing sequence142. The second mobile device 76 includes a beaconing indicator 120 thatflashes the yellow green beaconing sequence 144. The third mobile device136 includes a screen 121 that flashes an orange blue sequence 146. Afourth user 138 holding a fourth mobile device 140 is flashing a red offbeaconing sequence 148

The compass 116 can eliminate the fourth user 138 from consideration,because it points away from the fourth mobile device 140 as shown inFIG. 8. However, the compass 116 points toward the first mobile device74 and the third mobile device 136. The second user 128 can distinguishthe first user 126 from the third user 134, however, because the orangeblue beaconing sequence 146 contrasts with the yellow green beaconingsequence 144 on the beaconing indicator 120. The beaconing sequences142, 144 can be synchronized to assure the second user 128 that it isthe first user 126.

FIG. 10 illustrates a variety of beaconing sequences which can beassigned to a given mobile device by the first server 10. As shown, abeaconing sequence is a combination of colors, timing, icons and textdelivered in segments that will enable a user to locate another user ofinterest in a crowd. For example, the beaconing sequence could simply bea single color such as yellow 150 that is displayed. To increasevisibility, the beaconing sequence could be a flashing color such as red152, multiple alternating colors such as yellow-green-yellow 154, ormultiple colors in a repeating sequence of segments such as red, white,and blue 156. Further, the beaconing sequence can be multiple colorsdisplayed at the same time such a segment of yellow/green 158, or anicon (static or dynamic) on a background color(s) such orange 160, or anicon on alternating background colors such as red and gold 162, or anon-repeating sequence of multiple colors 164.

FIGS. 11-12 illustrate assigning beaconing sequences in a location cellthat would be useful in a crowded environment such as Times Square.Let's assume the second user 128 is at the corner of W. 47th Street andBroadway looking for the first user 126 who is at W. 46th Street and 7thAvenue at about 10 PM on December 31st, just before the New Yearcelebration. A third user 134 is at 46th and Broadway and a fourth user138 at W. 49th Street and Broadway. The third user 134 and fourth user138 are using the application, but are not in the same group as definedby the first user 126 which included only the second user 128. The thirduser 134 with a mobile device 136 is assigned an orange-blue beaconingsequence 254. Since the first user 126 and the third user 134 are in thesame location cell 240, to avoid a conflict the first server 10 assignsa different beaconing sequence such the yellow-green sequence 250 to bedisplayed on the first mobile device 74 of the first user 126. Incontrast, the fourth user 138 with mobile device 140 in a non-adjacentcell such as location cell 244 can be assigned a similar yellow-greenbeaconing sequence 256. The first server 10 can extend the assignment ofthe unique beaconing sequences for each location cell beyond thelocation cell 240 of the first user 126 and the location cell 242 of thesecond user 128 to one or more surrounding location cells such as celllocation 246, which is non-adjacent to location cell 240. FIG. 11illustrates the location cells as hexagonal, but it could be a varietyof geometric planar shapes such as a square, a rectangular, circle, or atriangle, or any shape that can be arranged in a grid or a geometric 3Dshapes such as a cube, a cylinder, or a prism.

FIGS. 13-14 illustrate assigning beaconing sequences by venue that wouldbe useful in adjacent venues such as an amusement park, a stadium and ashared parking lot. Initially, the first user 126 with a mobile device74 and the fourth user 138 with a mobile device 140 are both in thefirst venue 258 (e.g., the shared parking lot). In the first venue 258,the first server 10 has assigned a yellow blue beaconing sequence 268 tothe first mobile device 74, and the flashing red beaconing sequence 272to the fourth mobile device 140. The first and fourth users 126, 138 areboth using the application, but are not in the same group. Next, thefourth user 138 travels to a location 266 in a second venue 260 (e.g., asports stadium). Since no other user is assigned the flashing redbeaconing sequence 272 in the second venue 260, the fourth user 138 cancontinue using it. In contrast, when the first user 126 travels to alocation 264 in a third venue 262 (e.g., an amusement park), the firstserver 10 will assign the flashing red beaconing sequence 274 to thefirst mobile device 74 to avoid a conflict with the third user 134 whosemobile device 136 was previously assigned the yellow blue beaconingsequence 278 in the third venue 262. Now the second user 128 can readilyfind the first user 126 using the same flashing read beaconing sequence274 and 276.

FIG. 15 illustrates a flow diagram for the beaconing logic that runs onthe server of FIGS. 1 and 3. Hunter et al., Java Servlet Programming(2001) describes Java Servlet programming that can be used to implementthe beaconing logic and is incorporated by reference herein. As shown inFIG. 15, the beacon logic 32 (FIG. 1) that runs in the first server 10begins when the second user 128 presses the wave request button 118 onthe screen 114 of the second mobile device 76 (FIG. 2E). The secondmobile device 76 will send a request (e.g., HTTP request) to the firstserver 10. At step 164, the first server 10 will read the request, whichincludes the clock value of the second mobile device 76. At step 168,the first server 10 will read the location of the first and secondmobile devices 74, 76. The first server 10 will perform a time sync thatreads its own clock and receives the time stamp of each of the first andsecond mobile devices 74, 76. As a reminder, the first mobile device 74also performs a time sync (e.g., FIG. 3, Start of App 125) that includesa clock value of the first mobile device 74. In an embodiment, the timesync can be performed multiple times and averaged. The time sync may bedone once or periodically, and will depend on accuracy of the mobiledevice clocks, and clock drift. Any difference between the clocks isstored in a memory accessible to the first server 10, and represents anoffset that can be used to ensure the beaconing sequence of the firstmobile device 74 and the second mobile device 76 are on the same clock.At step 170, the first server 10 will look up the beaconing sequencehistory table, which is stored in the database 24. Each record in thetable will contain: beaconing sequence, the geographic location, and thetime of the sequence. At step 172, the beacon logic 32 will execute adatabase query that filters on location and time so that only recentbeaconing sequences from other users in the area will be in the result.If there are no recent beaconing sequences used by other users in thearea, the beacon logic 32 will move to step 174. At step 174, the beaconlogic 32 will perform a lookup of the first user's preference for abeaconing sequence. At step 176, the beacon logic 32 will calculate thebeaconing sequence from the preference of the first user 74.

If there are recent beaconing sequences used by other users in the areaat step 172, the beacon logic 32 will move to step 178. At step 178, thebeacon logic 32 will read the record of the beacon sequence in thebeaconing sequence history table that was recently used in the area. Atstep 180, the beacon logic 32 will add the beacon sequence to a sequencelist that contains all the beacon sequences that cannot be used in thearea by the first user 126. At step 182, the beacon logic 32 willdetermine if there is another record returned from the query of thedatabase 24. If yes, the beacon logic 32 will return to read the nextbeacon history record. This loop continues until all of the beaconsequence records are processed. If no, the beacon logic 32 will go tostep 184. At step 184, the beacon logic 32 will calculate the beaconsequence that will be used by the first user 126. In an embodiment, thiscalculation can optimize the difference between the color(s) in thebeaconing sequence to be used by the first user 126 and those already inuse. At step 186, the beacon logic 32 adds the calculated beaconsequence to the beacon history table. At step 188, the beacon logic 32sends a response with the calculated beacon sequence 126, which isreceived by the first mobile device 74 at step 120 (FIG. 3).

FIG. 16 illustrates a flow diagram for the message logic that runs inthe server of FIGS. 1 and 3. The first user 74 will complete the fieldsshown in FIG. 2C. As shown in FIG. 2C, the screen 102 displays thefields: an event name 101, a start time 103, an end time 105, and a listof guests 104. In an embodiment, the list of guests 104 is the emailaddresses of the guests.

Referring to FIG. 16, at step 106, the first user 126 presses the sendbutton 106 (FIG. 2C), which causes the first mobile device 74 to send arequest 300 to the first server 10. The request 300 includes theinformation that the user input into one or more of the fields shown inFIG. 2C. The message logic 28 reads the request at step 190. At step192, the message logic 28 adds the request information as an entry intothe Event table in the database 24. At step 194, the message logic 28will read the identifying information (e.g., email address or cell phonenumber) of the next guest in the list 104 (FIG. 2C). At step 196, themessage logic 28 will perform a lookup in the user in the database 24.At step 198, the message logic 28 will check if the user has theapplication. If yes, the message logic 28 will add an entry in the userevent table at step 202. Next, at step 204, the message logic 28 willperform a lookup of the user's notification preferences (e.g., email,text message, push notification, automated phone call, or a social mediapost). At step 206, the message logic 28 will send a notification usingthe preferred method(s) to the second mobile device 76. In addition, themessage logic 28 will send a message to add an entry 107 to the findthings screen 108 (FIG. 2D) of the second mobile device 76. Next, atstep 208, the message logic 28 will check if another user is on theguest list. If yes, the message logic 28 will return to step 194. Ifnot, that is, it was the last user on the guest list, the message logic28 will send a response 304 (FIG. 3) to the first mobile device 74 atstep 210. As a result, a confirmation is received by the first mobiledevice 74 at step 211.

FIG. 17 illustrates a flow diagram for the event logic that runs on theserver of FIGS. 1 and 3. At step 92, the second user 128 will press thefind things button 92 (FIG. 2A) on the second mobile device 76, whichsends a request 306 to complete the find things screen to the firstserver 10. At step 212, the first server 10 reads the request thatincludes the identity of the second user 128. At step 214, the eventlogic 30 will perform a lookup of all entries for the second user 128 inthe user event table in the database 24. The event logic 30 will readeach entry from the user event table at step 216. At step 218, the eventlogic 30 will add the information from the entry to the find things listthat will eventually be returned to the second mobile device 76 tocreate the find things screen 108 in FIG. 2D. At step 220, the eventlogic 30 will read if another entry exists in the user event table. Ifyes, the event logic 30 will return to step 216. If no, the event logic30 will go to step 222. The event logic 30 will prioritize the findthings list at step 222 then send it in a response 308 (FIG. 3) at step228 to generate the screen 108 (FIG. 2D) with entries pertaining to thesecond user 128 on the second mobile device 76.

FIG. 18A-18F is a set of flow diagrams that illustrate the applicationlogic that runs on the mobile device.

FIG. 18A illustrates the application that runs on the mobile device. Theapplication 64 includes communication interface 66, the applicationlogic 68, and the user interface 70. At step 352, the application logic68 will use the communication interface 66 to send a time stamp asdescribed in FIG. 3. At step 354, the application logic 68 uses the userinterface 70 to draw the screen 88 shown in FIG. 2A. At step 356, theapplication logic 68 determines if the user pressed the remember placebutton 89 shown in FIG. 2A. If yes, the application logic 68 exits toentry point B on FIG. 18B. If no, the application logic 68 goes to step360. At step 360, the application logic 68 determines if the userpressed the share location button 90 shown in FIG. 2A. If yes, theapplication logic 68 exits to entry point C on FIG. 18C. If not, theapplication logic 68 goes to step 364. At step 364, the applicationlogic 68 determines if the user pressed the find things button 92 shownin FIG. 2A. If yes, the application logic 68 exits to entry point D onFIG. 18D. If no, the application logic 68 goes to step 368. At step 368,the application logic 68 waits a time period (e.g., 10 ms) then goes tostep 356.

FIG. 18B illustrates the application that runs on the mobile device. Atstep 370, the application logic 68 uses the user interface 70 to drawthe screen 94 shown in FIG. 2B. At step 372, the application logic 68determines if the user pressed the save place button 98 shown in FIG.2B. If yes, the application logic 68 goes to the remember place at step374. At step 374, the application logic 68 stores the current locationin the memory of the mobile device and optionally sends the locationinformation to be stored on the first server 10 and preferably thedatabase 24. The application logic 68 exits to entry point A on FIG.18A. At step 376, the application logic 68 determines if the userpressed the add picture button 95 shown in FIG. 2B. If yes, theapplication logic 68 will show the camera at step 378. At step 380, theapplication logic 68 stores the picture (e.g., a landmark near the placeto be remembered) in the memory of the mobile device and optionallysends the picture to be stored on the first server 10 and preferably thedatabase 24. At step 382, the application logic 68 determines if theuser pressed the add memo button 97 shown in FIG. 2B. If yes, theapplication logic 68 goes to record voice feature at step 384. At step386, the application logic 68 stores the voice memo (e.g., a descriptionabout the place to be remembered) in the memory of the mobile device andoptionally sends the recorded voice memo to be stored on the firstserver 10 and preferably the storage 24. At step 388, the applicationlogic 68 determines if the user pressed the add text note button 99shown in FIG. 2B. If yes, the application logic 68 uses the userinterface 70 to show a keyboard at step 390. At step 392, theapplication logic 68 stores the text note (e.g., a text note about theplace to be remembered) in the memory of the mobile device andoptionally sends the text note to be stored on the first server 10 andpreferably the database 24. If the user did not press buttons 95, 97,98, or 99, the application logic 68 will determine if the user pressedthe back button 100 as shown in FIG. 2B at step 394. If not, applicationlogic 68 waits a time period (e.g., 10 ms) at step 396. After steps 380,386, and 392, the application logic 68 waits at step 396.

FIG. 18C illustrates another feature of the application that runs on themobile device. FIG. 18C begins by entering from point C on FIG. 18A. Atstep 398, the application logic 68 uses the user interface 70 to drawthe share location screen 102 shown in FIG. 2C. The input fields ofshare location screen 102 are initially empty (not shown). At step 399,the user will enter values into the input fields as previously shown inFIG. 2C. At step 400, if the user presses the back button 100 (FIG. 2C),the application logic 68 will go to entry point A on FIG. 18A to drawthe home screen 88 shown in FIG. 2A. If not, the application logic 68will determine if the user pressed the send button 106 as shown in FIG.2C. If not, the application logic 68 waits a time period (e.g., 10 ms)at step 408. If yes, the application logic 68 will determine if the userinput is valid at step 404. If not, the application logic 68 will notifythe user that the input is not valid at step 410. If yes, theapplication logic 68 will send share location information to be storedon the first server 10 and preferably on the database 24 at step 406. Atstep 412, the server will send a response to the mobile device then theapplication logic 68 exits to entry point A on FIG. 18A.

FIG. 18D illustrates another feature of the application that runs on themobile device. FIG. 18D begins by entering from point D on FIG. 18A orFIG. 18E. At step 414, the application logic 68 will send a request withthe identity of the user to the first server 10 (FIG. 1). The eventlogic 30 will use the user identity to look up all of the entries ofthat user in the user event table then prepare a find things list whichwill be returned in a response to the user's mobile device. Theapplication logic 68 of the mobile device will parse the response atstep 416. At step 418, the application logic 68 will draw the findthings screen 108 in FIG. 2D. At step 420, the application logic 68 willupdate the status text in each entry of the find things screen 108.Referring to screen 108 on FIG. 2D, the entry 107 (e.g., Alan @ Concert)the status text is “200 feet NW.” In contrast, the “Alan @ Concert” willnot change and thus will not be updated. If not, at step 424, theapplication logic 68 determines if the second user 128 pressed any ofthe find buttons such as button 110, 112, 117, or 119 as shown in FIG.2D. If yes, the application logic 68 will go to entry point E on FIG.18E. If not, the application logic 68 goes to step 428 to determine ifthe second user 128 switched any visibility button on or off (FIG. 2D,button 111 is on, and button 113 is off). When the visibility switch 111is “on” the second user 128 (e.g., Bob) is visible to the first user 126(e.g., Alan) and if the switch 111 is “off” the second user 128 is notvisible. The visibility switch could be referred to as a toggle button.At step 430, the application logic 68 uses communication interface 66 tocall the first server 10 to change the visibility settings for thesecond user 128 in database 24. At step 432, the application logic 68will wait for a time period (e.g., 10 ms) then proceed to step 420.

FIG. 18E illustrates another feature of the application that runs on themobile device. FIG. 18E begins by entering from point E on FIG. 18D. Atstep 434, the application logic 68 uses the communication interface 66to call the first server 10 to get user locations. At step 436, theapplication logic 68 calculates the distance between users and updatesthe compass 116 on the screen 114 shown in FIG. 2E. At step 440, theapplication logic 68 will determine if there is a beacon notification onthe first mobile device 74. If yes, the application logic 68 will read abeacon sequence at step 442, and at step 448 draw the screen 122 shownin FIG. 2F. At step 450, the application logic 68 updates a segment ofthe beaconing sequence, then waits until the end of the segment at step454 then determines if the beaconing sequence is finished at step 456.If not, the application logic 68 will repeat the loop beginning at step450. If the beaconing sequence is finished, the application logic 68will draw another screen (e.g., FIG. 2A, 2D, or 2E or a message screen(e.g., text or voice) to allow the first user 126 to communicate andassist in finding the second user 128 at step 457. At step 453, theapplication logic 68 will wait for a time period (e.g., 10 ms) thenproceed to step 436.

FIG. 18F illustrates an embodiment of the application that runs on themobile device. FIG. 18F begins by entering from point F on FIG. 18E. Atstep 458, the application logic 68 uses the communication interface 66to call the first server 10 to get the beacon sequence for the beaconindicator 120 on the screen 114 as shown in FIG. 2E. At step 460, theapplication logic 68 reads the beacon sequence and updates the beaconindicator 120 (FIG. 2E) at step 464. At step 466, the application logic68 will wait until the end of the current segment of the beacon sequencethen proceeds to step 468. At step 468, the application logic 68 willdetermine if it is the last segment of the beacon sequence, that is, thebeacon sequence is finished. If yes, the application logic 68 will exitto entry point E on FIG. 18E.

What is claimed:
 1. A method implemented in a server for providing aunique beaconing sequence to an electronic wearable and a mobile devicein a geographic area so a user of the electronic wearable and a user ofthe mobile device can locate each other, comprising: receiving a requestfrom the mobile device; reading the request; reading a beacon historytable in response to the request read; in response to the reading,determining if there are beacon sequences used in the geographic area;in response to the determining, calculating a unique beacon sequence notused in the geographic area; adding the unique beacon sequence to thebeacon history table; and sending the unique beacon sequence for displayon the electronic wearable and the mobile device, wherein the displayedunique beacon sequence is conspicuous and can be seen by the user of theelectronic wearable and the user of the mobile device in the geographicarea so that the user of the electronic wearable and the user of themobile device can locate each other.
 2. The method of claim 1, whereinthe unique beacon sequence for display on the electronic wearable isvisibly different from the other beacon sequences used in the geographicarea.
 3. The method of claim 1, further comprising updating coordinatesfor a compass on the mobile device that indicates the location of theelectronic wearable.
 4. The method of claim 3, wherein the mobile deviceis a smart watch.
 5. The method of claim 1, further comprising computingan offset for displaying the unique beacon sequence at that same time onthe electronic wearable and the mobile device.
 6. The method of claim 1,further comprising using venue or cell location to determine thegeographic area.
 7. A method implemented in a server for providing aunique beaconing sequence to an electronic wearable and a mobile devicein a geographic area so a user of the electronic wearable and a user ofthe mobile device can locate each other, comprising: receiving a requestfrom the electronic wearable; reading the request; reading a beaconhistory table in response to the request read; in response to thereading, determining if there are beacon sequences used in thegeographic area; in response to the determining, calculating a uniquebeacon sequence not used in the geographic area; adding the uniquebeacon sequence to the beacon history table; and sending the uniquebeacon sequence for display on the electronic wearable and the mobiledevice, wherein the displayed unique beacon sequence is conspicuous andcan be seen by the user of the mobile device and the user of theelectronic wearable in the geographic area so that the user of theelectronic wearable and the user of the mobile device can locate eachother.
 8. The method of claim 7, wherein the unique beacon sequence fordisplay on the electronic wearable is visibly different from the otherbeacon sequences used in the geographic area.
 9. The method of claim 7,further comprising updating coordinates for a compass on the electronicwearable that indicates the location of the mobile device.
 10. Themethod of claim 9, wherein the mobile device is a smart watch.
 11. Themethod of claim 7, further comprising computing an offset for displayingthe unique beacon sequence at that same time on the electronic wearableand the mobile device.
 12. The method of claim 7, further comprisingusing venue or cell location to determine the geographic area.
 13. Amethod implemented in a server for providing a unique beaconing sequenceto a first electronic wearable and a second electronic wearable in ageographic area so a first user of the electronic wearable and a seconduser of the second electronic wearable can locate each other,comprising: receiving a request from the first electronic wearable;reading the request; reading a beacon history table in response to therequest read; in response to the reading, determining if there arebeacon sequences used in the geographic area; in response to thedetermining, calculating a unique beacon sequence not used in thegeographic area; adding the unique beacon sequence to the beacon historytable; and sending the unique beacon sequence for display on the firstelectronic wearable and the second electronic wearable, wherein thedisplayed unique beacon sequence is conspicuous and can be seen by thefirst user and the second user in the geographic area so that the firstuser of the first electronic wearable and the second user of the secondelectronic wearable can locate each other.
 14. The method of claim 13,wherein the unique beacon sequence for display on the first and secondelectronic wearables is visibly different from the other beaconsequences used in the geographic area.
 15. The method of claim 13,further comprising updating coordinates for a compass on the secondelectronic wearable that indicates the location of the first electronicwearable.
 16. The method of claim 13, further comprising computing anoffset for displaying the unique beacon sequence at that same time onthe first electronic wearable and the second electronic wearable. 17.The method of claim 13, further comprising using venue or cell locationto determine the geographic area.
 18. The method of claim 13, whereinthe first and second electronic wearables are smart watches.